Wrap vendored modules to avoid build conflicts #250
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This FYI PR renames the vendored Gluten, http/af, h2, websocket/af, to
Dream_gluten
, etc., to avoid conflicts with versions of these modules installed from opam.I took a different, much less invasive and much more maintainable approach to the renaming than in #200. I used that we replace all the
dune
files of the vendored modules withsrc/vendor/dune
to wrap e.g.Gluten
asDream_gluten.Gluten
, and then added module aliases at the top of each file that usedGluten
, somodule Gluten = Dream_gluten.Gluten
. This is in contrast to #200, which renamed theGluten
toDream_gluten
throughout the code in all the files, and renamed the files. I will check that this truly doesn't conflict with parallel installations of the "real"Gluten
.I still have paf to rename afterwards, but it should go the same way as the other four libraries.
cc @clecat @anmonteiro @dinosaure @hannesm @TheLortex
Fixes #198.
Closes #200.